Skip to content

feat!: Replace flame_studio with the Flame component editor - #4178

Merged
erickzanardo merged 2 commits into
mainfrom
feat/replace-flame-studio-with-editor
Oct 30, 2026
Merged

erickzanardo merged 2 commits into
mainfrom
feat/replace-flame-studio-with-editor

Conversation

@erickzanardo

@erickzanardo erickzanardo commented Oct 30, 2026 •

Copy link
Copy Markdown
Member

Replace the in-game debugger with the flame_component_editor desktop app, which takes over the flame_studio name. The debugging features are moving to flame_devtools, tracked in #4176.

  • Add the app and its five packages to the workspace.
  • Narrow the workspace glob, since packages/** followed the plugin symlinks that Flutter generates in the platform folders.
  • Track the platform folders of the app.
  • Add a path-filtered flame_studio workflow and skip the app in cicd.yml.
  • Move the flame_bloc example to flutter_bloc 9 and equatable 3.

Description

Replaces the current flame_studio with the new approach of a standalone to help users build their project with visual tools

Checklist

  • I have followed the Contributor Guide when preparing my PR.
  • I have updated/added tests for ALL new/updated/fixed functionality.
  • I have updated/added relevant documentation in docs and added dartdoc comments with ///.
  • I have updated/added relevant examples in examples or docs.

Breaking Change?

  • Yes, this PR is a breaking change.
  • No, this PR is not a breaking change.

Related Issues

Comment thread packages/flame_studio/AGENTS.md Resolved
Comment thread packages/flame_studio/README.md Resolved
Replace the in-game debugger with the flame_component_editor desktop app,
which takes over the flame_studio name. The debugging features are moving
to flame_devtools, tracked in #4176.

- Add the app to the workspace, with its data and repository layers in
  lib/ instead of internal packages.
- Narrow the workspace glob, since `packages/**` followed the plugin
  symlinks that Flutter generates in the platform folders.
- Track the platform folders of the app.
- Use flame_lint with DCM on top of very_good_analysis and bloc_lint.
- Add a path-filtered flame_studio workflow and skip the app in cicd.yml.
- Move the flame_bloc example to flutter_bloc 9 and equatable 3.
@erickzanardo
erickzanardo force-pushed the feat/replace-flame-studio-with-editor branch from fbf1537 to f6e71a2 Compare October 30, 2026 20:31
@erickzanardo
erickzanardo requested a review from spydon October 30, 2026 20:42

@spydon spydon left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm!
Maybe there could be a subdirectory under lib that has what previously lived under packages/, but I'm fine with this too :)

Comment thread pubspec.yaml
@@ -3,7 +3,8 @@ repository: https://github.com/flame-engine/flame
workspace:
- doc/flame/examples
- doc/tutorials/**/app
- packages/**
- packages/*
- packages/*/*

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should probably not change?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one needs to stay.

With packages/**, pub also matches the plugin symlinks Flutter generates in packages/flame_studio/{linux,windows}/flutter/ephemeral/.plugin_symlinks, and once they exist flutter pub get fails with "does not have resolution: workspace".

Changing to packages/* and packages/*/* still cover every package we have and avoid the failure I mentioned above.

@erickzanardo
erickzanardo merged commit c973e65 into main Oct 30, 2026
8 checks passed
@erickzanardo
erickzanardo deleted the feat/replace-flame-studio-with-editor branch October 30, 2026 23:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants